Systems and methods of notifying a patient to take medication

ABSTRACT

Systems and methods of scheduling and sending notifications to, and receiving acknowledgements from, patients regarding specific health care events, such as the taking of medications at scheduled times and in prescribed dosages. By directing a patient to take their prescribed dosages of medication at scheduled times based on a schedule of medications prepared for the patient by a health care provider, a caregiver, etc., and enabling the patient to provide acknowledgements of having taken their prescribed dosages of medication, improved health care outcomes can be achieved. Further, by allowing the patient to receive such directives to take their medication, as well as to send such acknowledgements, using a set top box connected to a television set, a mobile device such as a mobile phone, and/or a patient notification device such as a wireless pendant, desired improvements in health care outcomes can be achieved with an increased level of convenience.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/875,597 filed May 2, 2013 entitled SYSTEMS AND METHODS OF NOTIFYING APATIENT TO TAKE MEDICATION.

BACKGROUND

In recent years, significant advances have been made in the developmentand availability of a variety of medications for treating a wide rangeof patient illnesses, diseases, and disabilities. As a result, healthcare providers have, in general, been prescribing medications to morepatients than ever before. In order for such medications to be most safeand effective, it is incumbent upon patients to take their prescribedmedications at the proper times and in the proper dosages. However, ithas become increasingly common for many patients to fail to adhere to astrict medical regimen, particularly with regard to the taking ofprescribed medications.

For example, many able-bodied patients lead busy lives that are filledwith work, meetings, travel, and family obligations, making complianceto a regular medication schedule difficult, if not virtually impossible.Children and elderly patients can have even more difficulty complyingwith their regular medication schedules. For example, health careproviders frequently prescribe a number of medications to their elderlypatients, who may, at times, forget or at least become confused withregard to what medications to take, as well as when to take them.Further, children are often prescribed medications that must be takenduring the busy school day, or some time after school when they may beinvolved in sports or other after-school activities that can distractthem from their regular medication schedules.

BRIEF DESCRIPTION OF EMBODIMENTS

In accordance with the present application, systems and methods aredisclosed for scheduling and sending notifications to, and receivingacknowledgements from, patients with regard to specific health careevents, such as the taking of medications at scheduled times and inprescribed dosages. The disclosed systems and methods allow patients toreceive directives to take medication, as well as send acknowledgementsof having taken their medication, using, e.g., a set top box connectedto a television set or other display device, a mobile device such as amobile phone, a patient notification device such as a wireless pendant,etc., thereby providing improved health care outcomes with an increasedlevel of convenience.

In one aspect, the disclosed system (also referred to herein as the“patient notification system”) includes a scheduling server, anauthentication server, a notification server, and an account informationdatabase. The scheduling server is communicably connectable, via apublic network such as the Internet, to at least one computerized deviceof a health care provider, a caregiver, or any other suitableindividual, such as a smartphone, or a desktop, laptop, or tabletcomputer. The notification server is communicably connectable to atleast one mobile device via the Internet or a wirelesstelecommunications network, and at least one network access device via avideo services network. For example, the network access device may be aset top box connected to a television set or other display device, andthe video services network may be a cable television (CATV) network oran Internet protocol television (IPTV) network. The notification serveris also communicably connectable, via an intelligent home network, to anintelligent home gateway, which, in turn, is communicably connected to apatient notification device, such as a wireless pendant.

In an exemplary mode of operation, the health care provider, thecaregiver, etc., can employ his or her computerized device to securelyaccess the scheduling server within the patient notification system overthe Internet. For example, the health care provider, the caregiver,etc., may securely access the scheduling server through a webpage orsoftware application running on the computerized device, and providecredentials such as a username/password combination that verifies him orher to the scheduling server, as well as a patient account number thatallows him or her to prepare a personalized schedule of medications fora particular patient via the webpage or software application.

Once the health care provider, the caregiver, etc., is verified to thescheduling server and the patient's schedule of medications iscompleted, the scheduling server establishes a secure connection to theauthentication server, and directs the authentication server to querythe account information database to obtain personalized informationpertaining to one or more patient notification devices associated withthe patient account number. For example, the patient notificationdevices may include the set top box, the mobile device, the wirelesspendant, and/or any other suitable wired or wireless device. Further,the personalized information pertaining to the patient notificationdevices may include a unique identification code designed to avoiddirect association of the personalized information with the patient, aswell as a list of reference numbers, device types, and addressableinformation for the respective notification devices. The authenticationserver securely sends the unique identification code and the list ofreference numbers to the scheduling server, and securely sends theunique identification code, the list of reference numbers, the devicetypes, and the addressable information for the respective notificationdevices to the notification server.

The schedule of medications prepared for the patient by the health careprovider, the caregiver, etc., may include information pertaining to oneor more health care events, such as times during one or more 24-hourperiods when prescribed dosages of one or more medications are to betaken by the patient. Upon completion of the schedule of medications, orat any other suitable time, the scheduling server processes the scheduleof medications, and, based on that schedule of medications, monitors fora health care event to occur, such as the detection of a time during a24-hour period when the patient is scheduled to take a prescribed dosageof medication.

Once the scheduled time for taking the prescribed dosage of medicationis detected, the scheduling server securely sends, to the notificationserver, a message including the unique identification code and the listof reference numbers for the respective notification devices associatedwith the patient. The notification server processes the message from thescheduling server to determine the device types for the respectivenotification devices, based at least on the unique identification codeand the list of reference numbers contained in the message.

In the event the device types for the patient notification devicesinclude the set top box, the notification server securely sends anotification message to the set top box via the video services network,using the addressable information for the set top box provided by theauthentication server. Further, a software application running on theset top box monitors for receipt of such a notification message, and, inresponse to the receipt of the notification message, causes acorresponding video and/or audio notification to be presented on thetelevision set or other display device connected thereto. For example,the set top box may cause the television set or display device tovisibly and/or audibly present the notification, “It is now time forDoris to take one 20 mg tablet of cholesterol-lowering medication”.After the patient, Doris, takes the prescribed dosage of medication, sheprovides an acknowledgement of having taken the medication to thenotification server. For example, the patient, Doris, may employ aremote control device to send a specified acknowledgement signal to theset top box, which, in turn, securely forwards Doris's acknowledgementof having taken the medication to the notification server over the videoservices network.

In the event the device types for the patient notification devicesfurther include the mobile device, the notification server can securelysend a notification message to the mobile device via the Internet or thewireless telecommunications network, using the addressable informationfor the mobile device provided by the authentication server. Further, asoftware application running on the mobile device monitors for receiptof such a notification message, and, in response to the receipt of thenotification message, causes a corresponding video and/or audionotification to be presented on the mobile device. For example, themobile device may visibly and/or audibly present the same or similarnotification, “It is now time for Doris to take one 20 mg tablet ofcholesterol-lowering medication”. If she has not already done so, thepatient, Doris, can provide her acknowledgement of having taken themedication to the notification server using the mobile device, securelysending a specified message of acknowledgment to the notification serverover the Internet or the wireless telecommunications network.

In the event the device types for the patient notification devicesfurther include the wireless pendant, the notification server cansecurely send a notification message to the intelligent home gateway viathe intelligent home network, using the addressable information for theintelligent home gateway provided by the authentication server. Further,a software application running on the intelligent home gateway monitorsfor receipt of such a notification message, and, in response to thereceipt of the notification message, causes a corresponding visible,audible, and/or vibration notification to be presented on the wirelesspendant. For example, the wireless pendant may visibly and/or audiblypresent the same or similar notification, “It is now time for Doris totake one 20 mg tablet of cholesterol-lowering medication”. If she hasnot already done so, the patient, Doris, can provide an acknowledgementof having taken the medication to the notification server using eitherthe wireless pendant or the intelligent home gateway, securely sending aspecified message of acknowledgment to the notification server over theintelligent home network.

Having received the patient acknowledgement provided by the set top box,the mobile device, or the wireless pendant/intelligent home gateway, thenotification server securely forwards the acknowledgement to thescheduling server, which securely records the acknowledgement in memoryand/or any other suitable data storage. The notification server may alsosecurely forward the patient acknowledgement to the computerized deviceof the health care provider, the caregiver, etc., over the Internet forsecure storage in association with the computerized device.

In the event the notification server does not receive an acknowledgementfrom the patient within a predetermined time period, the notificationserver can notify the scheduling server and/or the computerized deviceof the health care provider, the caregiver, etc., of its failure toreceive the patient acknowledgement. Further, the scheduling server, thecomputerized device of the health care provider, the caregiver, etc.,and/or the health care provider or caregiver himself/herself can takeappropriate steps in response to the failure to receive the patientacknowledgement. For example, the scheduling server or the computerizeddevice of the health care provider, the caregiver, etc., can send, viathe notification server, an emergency message to the set top box, themobile device, the wireless pendant, and/or to a specified telephonenumber to alert emergency services. At a desired time, the health careprovider, the caregiver, etc., can employ his or her computerized deviceto securely access the scheduling server to obtain a report of thevarious notifications sent to, as well as the correspondingacknowledgements received from, his or her patient.

By directing a patient to take one or more specified actions, such asthe taking of one or more prescribed dosages of medication at one ormore scheduled times based on a schedule of medications prepared for thepatient, and enabling the patient to provide acknowledgements of havingtaken their prescribed dosages of medication, improved health careoutcomes can be achieved. Further, by allowing the patient to receivesuch directives to take medication as well as send acknowledgements ofhaving taken their medication using a set top box connected to atelevision set, a mobile device such as a mobile phone, and/or a patientnotification device such as a wireless pendant, desired improvements inhealth care outcomes can be achieved with an increased level ofconvenience.

It is noted that the ordering of various steps and/or actions performedin the exemplary mode of operation described above has been provided forpurposes of illustration, and that the various steps/actions asdescribed herein can be performed in any suitable order. It is furthernoted that other aspects of the present application can include softwareprograms and/or hardware operative to perform any of the steps/actionssummarized above and described in further detail below.

It is to be understood that systems, methods, apparatus, instructions oncomputer readable storage media, etc., as described herein, can beembodied as one or more software programs, firmware, a hybrid ofsoftware, hardware, and/or firmware, or hardware alone, such as withinone or more processors, operating systems, and/or software applications.It is to be further understood that the various servers describedherein, including the scheduling server, the authentication server,and/or the notification server within the patient notification system,can be embodied as one or more processes implemented in software,hardware, firmware, or any suitable combination thereof, on one or morecomputers or any other suitable computerized devices and/or one or morecomputerized components implemented in software, hardware, firmware, orany suitable combination thereof.

Various techniques described herein are well suited for processingpatient notifications. It should be noted, however, that the techniquesdescribed herein are not limited to use in such applications, and thatthe techniques described herein are suited for other applications aswell.

In addition, although each of the different features, techniques,configurations, etc., described herein may be discussed in differentplaces within the present application, it is intended, where suitable,that each of these concepts can be executed independently of, or incombination with, each other. Accordingly, the various aspects of thepresent application, as described herein, can be embodied and viewed inmany different ways.

It is noted that this preliminary discussion of the various aspects ofthe present application does not specify every aspect of the applicationor claimed invention(s). Rather, this discussion presents generalembodiments and corresponding points of novelty over conventionaltechniques. For further details and/or possible perspectives(permutations) of the claimed invention(s), the reader is directed tothe Detailed Description and corresponding drawing figures of thepresent application, as provided below.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more embodiments describedherein and, together with the Detailed Description, explain theseembodiments. In the drawings:

FIG. 1 is a diagram of an exemplary environment in which an exemplarypatient notification system may be employed, in accordance with thepresent application;

FIG. 2 is a diagram of exemplary signaling and/or messaging betweenvarious elements of the patient notification system within theenvironment of FIG. 1; and

FIG. 3 is a flow diagram of an exemplary method of operating the patientnotification system of FIG. 1.

DETAILED DESCRIPTION AND FURTHER SUMMARY OF EMBODIMENTS

The disclosure of U.S. patent application Ser. No. 13/875,597 filed May2, 2013 entitled SYSTEMS AND METHODS OF NOTIFYING A PATIENT TO TAKEMEDICATION is hereby incorporated herein by reference in its entirety.

Systems and methods are disclosed for scheduling and sendingnotifications to, and receiving acknowledgements from, patientsregarding specific health care events, such as the taking of medicationsat scheduled times and in prescribed dosages. The disclosed systems andmethods can direct a patient to take their prescribed dosages ofmedication at scheduled times based on a schedule of medicationsprepared for the patient by a health care provider, a caregiver, or anyother suitable individual, and enable the patient to provideacknowledgements of having taken their prescribed dosages of medication,thereby improving overall health care outcomes. The disclosed systemsand methods also allow the patient to receive such directives to takemedication, as well as send acknowledgements of having taken themedication, using a set top box connected to a television set, a mobiledevice such as a mobile phone, and/or a patient notification device suchas a wireless pendant, thereby allowing desired improvements in healthcare outcomes to be achieved with an increased level of convenience.

FIG. 1 depicts an exemplary environment 100 in which an illustrativeembodiment of a patient notification system 102 may be employed, inaccordance with the present application. As shown in FIG. 1, the patientnotification system 102 includes a scheduling server 104, anauthentication server 106, a notification server 110, and an accountinformation database 108. The scheduling server 104 is communicablyconnectable, via the Internet and/or a wired or wirelesstelecommunications network 112, to at least one computerized health careprovider device 114, such as a smartphone, a desktop computer, a laptopcomputer, a tablet computer, or any other suitable computerized device.The notification server 110 is communicably connectable to at least onemobile device 116 via the Internet/telecommunications network 112, andat least one network access device 120 via a video services network 118.For example, the mobile device 116 may be a mobile phone or any othersuitable mobile device. Further, the network access device 120 may be aset top box or any other suitable network access device connected to atelevision set or other display device 122. The set top box may be astandalone set top box, or a set top box incorporated into a cable-readytelevision set, and the display device 122 may be a personal computer orany other suitable display device. The video services network 118 may bea cable television (CATV) network, an Internet protocol television(IPTV) network, or any other suitable network. The notification server110 is also communicably connectable, via an intelligent home network126, to an intelligent home gateway 128, which, in turn, is communicablyconnected to a patient notification device 130, such as a wirelesspendant or any other suitable patient notification device, using WIFI or802.11 based communication, Bluetooth communication, Zigbeecommunication, or any other suitable wireless communication orcombination thereof.

In an illustrative mode of operation, a health care provider can employthe health care provider device 114 to securely access the schedulingserver 104 within the patient notification system 102 over the Internet.For example, the health care provider may securely access the schedulingserver through a webpage or software application running on the healthcare provider device 114, and provide credentials such as ausername/password combination, or any other suitable credentials, whichverify him or her to the scheduling server 104. The health care providermay also provide a patient account number that allows him or her toprepare a personalized schedule of medications for a particular patientvia the webpage or software application. It is noted that any othersuitable manner of securely accessing the scheduling server 104 from thehealth care provider device 114 may be employed.

Once the health care provider is verified to the scheduling server 104and the patient's schedule of medications is completed, the schedulingserver 104 establishes a secured connection 103 to the authenticationserver 106, and directs the authentication server 106 to query theaccount information database 108 to obtain personalized informationpertaining to one or more patient notification devices associated withthe patient account number. For example, the secured connection 103 mayinclude a secured authentication network protected with encryption, orany other suitable secured connection/network. Further, the patientnotification devices may include the network access device 120configured as a set top box, the mobile device 116 configured as amobile phone, the patient notification device 130 configured as awireless pendant, and/or any other suitable wired or wirelessnotification device. Moreover, the personalized information pertainingto the patient notification devices may include a unique identificationcode designed to avoid direct association of the personalizedinformation with the patient, as well as a list of reference numbers,device types, and addressable information for the respectivenotification devices. Such personalized information of a patient may bestored in the account information database 108 at a time when thepatient opts into a notification program implemented by the patientnotification system 102.

The authentication server 106 obtains the personalized informationassociated with the patient account number from the account informationdatabase 108 over a secured connection 105, which can include a securedpatient billing system network protected with encryption, or any othersuitable secured connection/network. The authentication server 106 sendsthe unique identification code and the list of reference numbers to thescheduling server 104 over the secured connection 103, and sends theunique identification code, the list of reference numbers, the devicetypes, and the addressable information for the respective notificationdevices to the notification server 110 over a secured connection 107,which, like the secured connection 103, may include the securedauthentication network protected with encryption, or any other suitablesecured connection/network.

It is noted that the schedule of medications prepared for the patient bythe health care provider may include information pertaining to one ormore health care events, such as times during one or more 24-hourperiods when prescribed dosages of one or more medications are to betaken by the patient. Upon completion of the schedule of medications, orat any other suitable time, the scheduling server 104 processes theschedule of medications, and, based on that schedule of medications,monitors for a health care event to occur, such as the detection of atime during a 24-hour period when the patient is scheduled to take aprescribed dosage of medication.

Once the scheduled time for taking the prescribed dosage of medicationis detected, the scheduling server 104 securely sends, to thenotification server 110, a message including the unique identificationcode and the list of reference numbers for the respective notificationdevices associated with the patient. For example, the scheduling server104 may send the unique identification code and the list of referencenumbers over another secured connection 109, such as a secured servicesnetwork protected with encryption, or any other suitable securedconnection/network. The notification server 110 processes the messagefrom the scheduling server 104 to determine the device types for therespective notification devices, based at least on the uniqueidentification code and the list of reference numbers contained in themessage.

As described herein, the device types for the patient notificationdevices can correspond to the network access device 120 configured as aset top box, the mobile device 116 configured as a mobile phone, and/orthe patient notification device 130 configured as a wireless pendant. Inthe event the patient notification devices include the set top box, thenotification server 110 securely sends a notification message to the settop box via the video services network 118, using the addressableinformation provided by the authentication server 106 and an appropriateprotocol for the set top box. For example, the video services network118 may include a secured set top box network protected with encryption,or any other suitable secured network.

The network access device 120 configured as a set top box includes atleast one processor 120 a operative to execute at least one softwareapplication out of at least one memory 120 b to monitor for receipt ofsuch a notification message, and, in response to the receipt of thenotification message, to cause a corresponding video and/or audionotification to be presented on the television set or other displaydevice 122 connected thereto. For example, the notification may includetext, video, audio, and/or at least one image. Further, the set top boxmay cause the television set or display device 122 to visibly and/oraudibly present a notification, such as, “It is now time for Gus to takeone 50 mg tablet of heart medication”. After the patient, Gus, takes theprescribed dosage of medication, he provides an acknowledgement ofhaving taken the medication to the notification server 110. For example,the patient, Gus, may employ a remote control device 124 to send aspecified acknowledgement signal to the set top box. Further, the remotecontrol device 124 may be configured to employ any suitable infrared(IR) or radio frequency (RF) signal for sending the acknowledgementsignal to the set top box. The software application executing within theset top box operates to detect the specified acknowledgement signal fromthe remote control device 124, and to securely forward Gus'sacknowledgement of having taken the medication to the notificationserver 110, e.g., as an out-of-band signal over the video servicesnetwork 118.

The scheduling server 104 further processes the schedule of medications,and monitors for another health care event to occur, such as thedetection of a time during a 24-hour period when the patient isscheduled to take another prescribed dosage of medication. Once thescheduled time for taking the next prescribed dosage of medication isdetected, the scheduling server 104 securely sends, to the notificationserver 110, another message including the unique identification code andthe list of reference numbers for the respective notification devicesassociated with the patient.

The notification server 110 processes the message from the schedulingserver 104 to determine the device types for the respective notificationdevices, based at least on the unique identification code and the listof reference numbers contained in the message.

In the event the patient notification devices further include the mobiledevice 116, the notification server 110 can securely send a notificationmessage to the mobile device 116 over the Internet/telecommunicationsnetwork 112, using the addressable information provided by theauthentication server 106 and an appropriate protocol for the mobiledevice 116. Like the set top box, the mobile device 116 isprocessor-based, and a software application executed by the processorwithin the mobile device 116 monitors for receipt of such a notificationmessage. In response to the receipt of the notification message, thesoftware application executing within the mobile device 116 causes acorresponding video and/or audio notification to be presented on themobile device 116. For example, the mobile device may visibly and/oraudibly present a notification, such as, “It is now time for Gus to takeone 20 mg tablet of cholesterol-lowering medication”. After the patient,Gus, takes the prescribed dosage of cholesterol-lowering medication, hecan provide his acknowledgement of having taken the medication to thenotification server 110 using the mobile device 116, securely sending aspecified message of acknowledgment to the notification server 110 overthe Internet/telecommunications network 112.

The scheduling server 104 continues to process the schedule ofmedications, and to monitor for still another health care event tooccur, such as the detection of a time during a 24-hour period when thepatient is scheduled to take a further prescribed dosage of medication.Once the scheduled time for taking the next prescribed dosage ofmedication is detected, the scheduling server 104 securely sends, to thenotification server 110, a further message including the uniqueidentification code and the list of reference numbers for the respectivenotification devices associated with the patient. The notificationserver 110 again processes the message from the scheduling server 104 todetermine the device types for the respective notification devices,based at least on the unique identification code and the list ofreference numbers contained in the message.

In the event the device types for the patient notification devicesfurther include the wireless pendant, the notification server 110 cansecurely send a notification message to the intelligent home gateway 128via the intelligent home network 126, using the addressable informationprovided by the authentication server 106 and an appropriate protocolfor the intelligent home gateway 128. A software application executed bythe intelligent home gateway 128 monitors for receipt of such anotification message, and, in response to the receipt of thenotification message, causes a corresponding visible, audible, and/orvibration notification to be presented on the wireless pendant. Forexample, the wireless pendant may visibly and/or audibly present, withor without vibration, a notification, such as, “It is now time for Gusto take one 75 mg tablet of blood-thinning medication”. After thepatient, Gus, takes the prescribed dosage of medication, he can providean acknowledgement of having taken the medication to the notificationserver 110 using the wireless pendant or the intelligent home gateway128, securely sending a specified message of acknowledgment to thenotification server 110 over the intelligent home network 126.

Having received the patient acknowledgements provided by the set topbox, the mobile device 116, and/or the wireless pendant/intelligent homegateway 128, the notification server 110 securely forwards eachacknowledgement over the secured connection 109 to the scheduling server104, which securely records the acknowledgement in memory and/or anyother suitable data storage. The notification server 110 may alsosecurely forward the patient acknowledgement to the health care providerdevice 114 over the Internet via e-mail, a push notification, etc., forsecure storage in association with the health care provider device 114.

In the event the notification server 110 does not receive anacknowledgement from the patient within a predetermined time period, thenotification server 110 can notify the scheduling server 104 and/or thehealth care provider device 114 of its failure to receive the patientacknowledgement. Further, the scheduling server 104, the health careprovider device 114, and/or the health care provider himself/herself cantake appropriate steps in response to the failure to receive the patientacknowledgement. For example, the scheduling server 104 or the healthcare provider device 114 can send an emergency message to the set topbox, the mobile device 116, and/or the wireless pendant/intelligent homegateway 128, and/or to a specified telephone number to alert emergencyservices. At a desired time, the health care provider can employ his orher computerized device 114 to securely access the scheduling server 104to obtain a report of the various notifications sent to, as well as thecorresponding acknowledgements received from, his or her patient.

In the illustrative mode of operating the patient notification system100 discussed above, it was described that a patient can receive aseries of notifications directing him or her to take medication via aset top box, a mobile device, a patient notification device, etc. It isnoted that, when opting into the notification program, patients canelect to receive such series of notifications via the same notificationdevice, or a plurality of different notification devices. In the event apatient elects to receive such notifications via multiple differentnotification devices, such as a television set connected to a set topbox, a mobile phone, and/or a wearable pendant, he or she need onlyprovide a single acknowledgement of having taken their prescribed dosageof medication at each scheduled time to the notification server 110,using a selected one of the respective notification devices. Thenotification server 110 securely forwards that single acknowledgementfrom the patient over the secured connection 109 to the schedulingserver 104, which securely records that acknowledgement in memory and/orother data storage.

It was further described herein that the scheduling server 104, thehealth care provider device 114, and/or the health care providerhimself/herself can take appropriate steps in response to a failure toreceive a patient's acknowledgement of having taken a prescribed dosageof medication at a scheduled time. To evaluate the status of such anon-responsive patient, the patient may be provided with one or morewearable wireless pendants that monitor one or more vital statistics ofthe patient, such as his or her blood pressure, heart rate, respiration,etc. Using WIFI or 802.11 based communication, Bluetooth communication,Zigbee communication, or any other suitable wireless communication, suchwireless pendants can provide the patient's blood pressure, heart rate,and/or respiration reading to the intelligent home gateway 128, whichcan securely forward the respective readings to the notification server110 over the intelligent home network 126. Any subsequent decisions toalert emergency services can then be based at least in part on themonitored vital statistics of the patient.

In some cases, a patient may be incapacitated to the extent that he orshe is not only incapable of providing an acknowledgement of havingtaken medication, but also incapable of taking their medication bythemselves. In one embodiment, the notification server 110 can beconfigured to send, at one or more scheduled times, one or more signalsto trigger a medical device for automatically administering a prescribeddosage of medication to the incapacitated patient. For example, thenotification server 110 may send a signal over theInternet/telecommunications network 112, the video services network 118,or the intelligent home network 126, for triggering a medical deviceoperative to administer the prescribed dosage of medicationintravenously to the patient. Further, the patient may be provided withone or more wearable wireless pendants that monitor one or more vitalstatistics of the patient, such as his or her blood pressure, heartrate, respiration, etc., thereby allowing a health care provider tomonitor the patient's status in response to having received theirmedication. In another embodiment, the notification server 110 can beconfigured to send, at one or more scheduled times, one or more signalsover the Internet/telecommunications network 112, the video servicesnetwork 118, or the intelligent home network 126, to actuate a pill boxfor dispensing a prescribed dosage of medication to a patient.

Exemplary signaling and/or messaging between the scheduling server 104,the authentication server 106, the notification server 110, and theaccount information database 108 within the patient notification system102, as well as between the various elements of the patient notificationsystem 102 and the health care provider device 114 and a patientnotification device (e.g., the network access device 120, the mobiledevice 116, or the wireless pendant/intelligent home gateway 128), isdescribed below with reference to FIG. 2. As shown in FIG. 2, the healthcare provider device 114 provides credentials that verify a health careprovider to the scheduling server 104 (see reference numeral 202). Oncethe health care provider is verified to the scheduling server 104, thehealth care provider completes a schedule of medications for at leastone patient, and the health care provider device 114 provides thepatient's schedule of medications to the scheduling server 104 (seereference numeral 204). The scheduling server 104 directs theauthentication server 106 to query the account information database 108to obtain personalized information pertaining to at least one patientnotification device associated with the patient (see reference numeral206). The authentication server 106 queries the account informationdatabase 108 for the requested personalized information (see referencenumeral 208), and the account information database 108 provides thepersonalized information (e.g., a unique identification code, a list ofreference numbers, device types, and addressable information for thepatient notification device(s)) to the authentication server 106 (seereference numeral 210). The authentication server 106 sends the uniqueidentification code and the list of reference numbers to the schedulingserver 104 (see reference numeral 212), and sends the uniqueidentification code, the list of reference numbers, the device types,and the addressable information for the respective notification deviceto the notification server 110 (see reference numeral 214).

Upon detection of a scheduled time for taking a prescribed dosage ofmedication, the scheduling server 104 sends, to the notification server110, a message including the unique identification code and the list ofreference numbers for the patient notification device associated withthe patient (see reference numeral 216). The notification server 110sends a notification message to the patient notification device usingthe addressable information for that notification device (see referencenumeral 218), directing the patient to take their prescribed dosage ofmedication. In response to receipt of the notification message, thepatient notification device presents a corresponding video, audio,and/or vibration notification on the respective notification device.Once the patient takes the prescribed dosage of medication, the patientoperates the patient notification device to send a specifiedacknowledgement signal to the notification server 110, indicating thathe or she has taken their medication (see reference numeral 220). Thenotification server 110 forwards the patient acknowledgement to thescheduling server 104, which records the acknowledgement in memoryand/or any other suitable storage (see reference numeral 222). At adesired time, using the health care provider device 114, the health careprovider requests, from the scheduling server 104, a report of thevarious notifications sent to, as well as the correspondingacknowledgements received from, his or her patient (see referencenumeral 224). In response to the health care provider's request, thescheduling server 104 provides the report to the health care providerdevice 114 (see reference numeral 226).

A method of operating the disclosed personal notification system 102 isdescribed below with reference to FIGS. 1 and 3. As depicted in block302, the scheduling server 104 monitors for a scheduled time to takemedication to occur. As depicted in block 304, upon detection of theoccurrence of the scheduled time, the scheduling server 104 sends, tothe notification server 110, a first message containing at least oneidentifier of the network access device 120 associated with the patient,in which the network access device 120 is communicably connectable tothe display device 122. As depicted in block 306, the notificationserver 110 sends, over the video services network 118, a notificationmessage to the network access device 120. As depicted in block 308, inresponse to receipt of the notification message at the network accessdevice 120, the network access device 120 causes a perceptiblenotification of the scheduled time to take the medication to bepresented to the patient on the display device 122. As depicted in block310, the notification server 110 receives, over the video servicesnetwork 118, an acknowledgement of the patient having taken themedication from the network access device 120.

In the above detailed description of the disclosed patient notificationsystems and methods, numerous specific details have been set forth toprovide a thorough understanding of claimed subject matter. However, itwill be understood by those skilled in the art that such claimed subjectmatter may be practiced without these specific details. In otherinstances, methods, apparatus, systems, etc., that would be known by oneof ordinary skill in the art have not been described in detail so as notto obscure the claimed subject matter. Some portions of the detaileddescription have been presented in terms of algorithms or symbolicrepresentations of operations on information, data, and/or signalsstored within memory, such as a computer memory. These algorithmicdescriptions or representations are examples of techniques used by thoseof ordinary skill in the data processing arts to convey the substance oftheir work to others skilled in the art. An algorithm as describedherein, and generally, is considered to be a self-consistent sequence ofoperations or similar processing steps leading to a desired result. Inthis context, such operations or processing steps involve physicalmanipulation of physical quantities. Typically, although notnecessarily, such quantities may take the form of electrical or magneticsignals capable of being stored, transferred, combined, compared, orotherwise manipulated. It has been convenient at times, principally forreasons of common usage, to refer to such signals as bits, data, values,elements, symbols, characters, terms, numbers, numerals, or the like. Itshould be understood, however, that all of these and similar terms areto be associated with appropriate physical quantities and are merelyconvenient labels. Unless specifically stated otherwise, it isappreciated that throughout this specification discussions utilizingterms such as “processing”, “computing”, “calculating”, “determining”,or the like refer to actions or processes of a computing platform, suchas a computer or a similar electronic computing device, that manipulatesor transforms data represented as physical electronic or magneticquantities within memories, registers, or other information storagedevices, transmission devices, or display devices of the computingplatform.

While this invention has been particularly shown and described withreferences to preferred embodiments thereof, it will be understood bythose skilled in the art that various changes in form and details may bemade therein without departing from the spirit and scope of the presentapplication, as defined by the appended claims. Such variations areintended to be covered by the scope of this present application. Assuch, the foregoing description of embodiments of the presentapplication is not intended to be limiting. Rather, any limitations tothe invention are presented in the following claims.

1. A method of providing at least one notification to, and receiving atleast one acknowledgement from, at least one patient with regard totaking medication at at least one scheduled time, comprising:monitoring, by a computerized scheduling component, for the scheduledtime to take the medication to occur; upon detection of the occurrenceof the scheduled time, sending, by the computerized scheduling componentto a computerized notification component, a first message containing atleast one identifier of at least one network access device associatedwith the patient, the network access device being communicablyconnectable to a display device; sending, by the computerizednotification component over at least one network, a notification messageto the network access device; in response to receipt of the notificationmessage at the network access device, causing, by the network accessdevice, a perceptible notification of the scheduled time to take themedication to be presented to the patient on the display device; andreceiving, at the computerized notification component over the network,an acknowledgement of the patient having taken the medication from thenetwork access device, the network including an Internet protocol (IP)network, wherein the sending of the notification message includessending, by the computerized notification component, the notificationmessage to the network access device over the IP network.
 2. The methodof claim 1 wherein the IP network is an Internet protocol television(IPTV) network, and wherein the sending of the notification messageincludes sending the notification message to the network access deviceover the IPTV network.
 3. The method of claim 2 further comprising:monitoring, by the network access device, for the receipt of thenotification message.
 4. The method of claim 3 wherein the causing ofthe perceptible notification to be presented on the display deviceincludes causing, by the network access device, one or more of a textnotification, a video notification, an audio notification, and an imagenotification to be presented to the patient on the display device. 5.The method of claim 1 further comprising: sending, by a remote controldevice, at least one signal indicative of the acknowledgement of thepatient having taken the medication to the network access device.
 6. Themethod of claim 5 wherein the sending of the signal to the networkaccess device includes sending, by the remote control device, one ormore of an infrared signal and a radio frequency signal indicative ofthe acknowledgement of the patient having taken the medication.
 7. Themethod of claim 1 further comprising: receiving, at the computerizedscheduling component from at least one computerized device, credentialsof at least one specified individual for use in verifying the specifiedindividual to the computerized scheduling component.
 8. The method ofclaim 7 further comprising: receiving, at the computerized schedulingcomponent from the computerized device, a patient account number for usein allowing the specified individual to prepare a schedule ofmedications for the patient on the computerized device.
 9. The method ofclaim 8 further comprising: receiving, at the computerized schedulingcomponent from the computerized device, the schedule of medications forthe patient, the schedule of medications including the scheduled timefor the patient to take the medication.
 10. The method of claim 9further comprising: directing, by the computerized scheduling component,a computerized authentication component to query an account informationdatabase for personalized information pertaining to the network accessdevice using the patient account number, the personalized informationincluding one or more of a unique identification code designed to avoiddirect association of the personalized information with the patient, atleast one reference number, at least one device type, and addressableinformation for the network access device.
 11. The method of claim 10further comprising: querying, by the computerized authenticationcomponent, the account information database for the personalizedinformation pertaining to the network access device.
 12. The method ofclaim 11 further comprising: sending, by the computerized authenticationcomponent, one or more of the unique identification code and thereference number to the computerized scheduling component; and sending,by the computerized authentication component, one or more of the uniqueidentification code, the reference number, the device type, and theaddressable information for the network access device to thecomputerized notification component.
 13. The method of claim 12 whereinthe sending of the first message includes sending, by the computerizedscheduling component, the first message containing one or more of theunique identification code and the reference number for the networkaccess device.
 14. The method of claim 13 wherein the sending of thenotification message to the network access device includes sending, bythe computerized notification component, the notification message to thenetwork access device using the addressable information for the networkaccess device.
 15. The method of claim 1 further comprising: forwarding,by the computerized notification component, the acknowledgement of thepatient having taken the medication to the computerized schedulingcomponent.
 16. The method of claim 15 further comprising: storing, bythe computerized scheduling component, the acknowledgement of thepatient having taken the medication in at least one data storage. 17.The method of claim 15 further comprising: sending, by the computerizedscheduling component, at least one report of one or more of thenotification message sent to, and the acknowledgement received from, thepatient.
 18. The method of claim 1 further comprising: in the event theacknowledgement of the patient having taken the medication is notreceived at the computerized notification component from the networkaccess device, notifying, by the computerized notification component,one or more of the computerized scheduling component and a computerizeddevice of a specified individual of a failure to receive theacknowledgement.
 19. The method of claim 18 further comprising: inresponse to the notification of the failure to receive theacknowledgement, sending, via the computerized notification component,an emergency message to at least the network access device.
 20. Apatient notification system, comprising: a notification server; anetwork access device associated with at least one patient; and ascheduling server, wherein the scheduling server is operative to monitorfor a scheduled time to take medication to occur, and, upon detection ofthe occurrence of the scheduled time, to send, to the notificationserver, a first message containing at least one identifier of thenetwork access device, the network access device being communicablyconnectable to a display device, wherein the notification server isoperative to send, over at least one network, a notification message tothe network access device, wherein the network access device isoperative, in response to receipt of the notification message, to causea perceptible notification of the scheduled time to take the medicationto be presented to the patient on the display device, wherein thenotification server is further operative to receive, over the network,an acknowledgement of the patient having taken the medication from thenetwork access device, wherein the network includes an Internet protocol(IP) network, and wherein the notification server is further operativeto send the notification message to the network access device over theIP network.
 21. The system of claim 20 wherein the IP network is anInternet protocol television (IPTV) network, and wherein thenotification server is further operative to send the notificationmessage to the network access device over the IPTV network.
 22. Thesystem of claim 21 wherein the notification server is further operativeto receive the acknowledgement of the patient having taken themedication from the network access device over the IPTV network.
 23. Thesystem of claim 20 wherein the notification server and the schedulingserver are implemented on one or more computers or computerized devices.24. A method of providing at least one notification to, and receiving atleast one acknowledgement from, at least one patient with regard totaking medication at at least one scheduled time, comprising:monitoring, by a computerized scheduling component, for the scheduledtime to take the medication to occur; upon detection of the occurrenceof the scheduled time, sending, by the computerized scheduling componentto a computerized notification component, a first message containing atleast one identifier of at least one patient notification deviceassociated with the patient; sending, by the computerized notificationcomponent over at least one network, a notification message to thepatient notification device; in response to receipt of the notificationmessage at the patient notification device, causing, by the patientnotification device, a perceptible notification of the scheduled time totake the medication to be presented to the patient; and receiving, atthe computerized notification component over the network, anacknowledgement of the patient having taken the medication from thepatient notification device, the network including an Internet protocol(IP) network, and wherein the sending of the notification messageincludes sending, by the computerized notification component, thenotification message to the network access device over the IP network.25. The method of claim 24 wherein the sending of the first messageincludes sending, to the computerized notification component, the firstmessage containing the identifier of the patient notification deviceconfigured as one of a mobile device, a network access device, and anintelligent home gateway.
 26. The method of claim 24 wherein the sendingof the notification message includes sending, by the computerizednotification component, the notification message to the patientnotification device over the network including one or more of theInternet, a telecommunications network, a video services network, and anintelligent home network.